fix(privacy): omit provider IDs from routine batch logs - #317

reviews:
  auto_review:
    drafts: true

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands.}

Fresh exact-head blocker RCA for #317@273a785642adcc5cb7ab72272a113e1ba6de8eae against protected main@b84f0c94154043a3473939c01bb6471de5a129ae:

• Required Strix Security is terminal failure at run 33350356643, job 99363187573.
• The trusted required workflow ran from central .github source SHA 046bc2beb2e0bb4be804255764bcbb4c49e973e9, materialized the exact PR head, and reached contextual-orchestrator provider routing.
• Gateway preflight found one ready route, nvidia_nim_meta_llama_3_2_90b_vision_instruct (meta/llama-3.2-90b-vision-instruct), but the actual Strix request failed before the first model response with provider HTTP 400 / invalid_request_error, retryable: false. Three bounded attempts failed the same way; each produced 0 tokens and no authoritative vulnerability analysis. The wrapper correctly failed closed as STRIX_PROVIDER_UNAVAILABLE.
• Therefore this failure is not evidence of a pg source/privacy defect and not evidence of zero vulnerabilities. Do not mutate this source lane to chase the provider failure; keep the PR Draft and require a fresh exact-head terminal Strix success after a material central/provider change.
• The aggregate coverage gate is separately non-passing because protected main still carries the two weakref branch arcs covered by dependency-root test(recovery): cover stale evidence registry cleanup #233. Do not duplicate test(recovery): cover stale evidence registry cleanup #233's active test writer here.

Writer-collision correction: a fresh non-default-branch comparison shows no-PR branch agent/retry-after-parser-hardening@417e84bee6356d560201d36a760425c3d893646d is 4 commits ahead / 187 behind protected main and also modifies pg_llm_batch/batch_api_client.py. That is active-writer evidence on the same production file even though the branch is stale/diverged. Freeze further source mutation on #317 for this invocation; reconcile ownership/non-overlap before any future change to this file. The current #317 diff itself remains exactly two commits ahead / zero behind main and changes only pg_llm_batch/batch_api_client.py plus its focused privacy test.